Systems and methods for connecting an audio controller to a hidden audio network

ABSTRACT

An example multimedia playback device is connected to a network that is configured to not provide an indicator of existence absent a command from the multimedia playback device. The example playback device is to initiate a connection phase for a device to connect to the hidden network based on a user action at the playback device. The example playback device is to reveal a network access point in a connection phase and authenticate the wireless device with the audio network for limited connectivity to the network during the connection phase. The example playback device is to disconnect the wireless device from the audio network and accept a connection of the wireless device to the audio network in an operational phase, the connection enabled using information provided to the wireless device during the connection phase and without the limited connectivity provided in the connection phase.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer electronics and, moreparticularly, to connect one or more devices to a playback data network.

BACKGROUND

Technological advancements have increased the accessibility of musiccontent, as well as other types of media, such as television content,movies, and interactive content. For example, a user can access audio,video, or both audio and video content over the Internet through anonline store, an Internet radio station, an online music service, anonline movie service, and the like, in addition to the more traditionalavenues of accessing audio and video content. Demand for such audio andvideo content continues to surge. Given the high demand, technology usedto access and play such content has likewise improved.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologyare better understood with regard to the following description, appendedclaims, and accompanying drawings where:

FIG. 1 shows an illustration of an example system in which embodimentsof the methods and apparatus disclosed herein can be implemented;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and speakers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example ad-hoc playback network;

FIG. 7 shows an example data exchange between two devices for deviceconfiguration with respect to a network;

FIGS. 8A-8B show flowcharts for example methods or processes forplayback device and network configuration;

FIG. 9 shows an example multimedia playback system in which a wirelessdevice is attempting to connect to an available network to playbackmultimedia content;

FIG. 10 depicts an example wireless device connecting to a network andmonitoring available network connections;

FIG. 11 illustrates a flow diagram for an example method to connect awireless device to a hidden network without the device or user networkthe network name or having to type in the network name; and

FIG. 12 illustrates a flow diagram for an example method to facilitateswitching between a wireless access point and a local node to access andcontrol a networked multimedia system.

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the present disclosure is notlimited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Wired or wireless networks can be used to connect one or more multimediaplayback devices for a home or other location playback network (e.g., ahome music system). Certain examples provide automatic configuration ofparameters of a playback device to be coupled to a network with reducedor minimum human intervention. For example, a wired and/or wirelessad-hoc network is established to facilitate communications among a groupof devices. When a new device is added to the network, a rudimentarycommunication path is initially established between one of the devices(“first device”) in the network and the new device (“second device”)such that parameters (e.g., service set identifier (SSID), Basic ServiceSet Identification (BSSID), Wired Equivalent Privacy (WEP) security,channel frequency, and so on) can be exchanged for the new device tofunction properly in the network. To help ensure the parameters areexchanged in a secure fashion, an additional public security procedurecan be used between the two devices, for example. To help ensure a goodconnection, a device can be configured to switch between availablenetworks based on observed network characteristics.

Although the following discloses example systems, methods, apparatus,and articles of manufacture including, among other components, firmwareand/or software executed on hardware, it should be noted that suchsystems, methods, apparatus, and/or articles of manufacture are merelyillustrative and should not be considered as limiting. For example, itis contemplated that any or all of these firmware, hardware, and/orsoftware components could be embodied exclusively in hardware,exclusively in software, exclusively in firmware, or in any combinationof hardware, software, and/or firmware. Accordingly, while the followingdescribes example systems, methods, apparatus, and/or articles ofmanufacture, the examples provided are not the only way(s) to implementsuch systems, methods, apparatus, and/or articles of manufacture.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

These embodiments and many additional embodiments are described morebelow. Further, the detailed description is presented largely in termsof illustrative environments, systems, procedures, steps, logic blocks,processing, and other symbolic representations that directly orindirectly resemble the operations of data processing devices coupled tonetworks. These process descriptions and representations are typicallyused by those skilled in the art to most effectively convey thesubstance of their work to others skilled in the art. Numerous specificdetails are set forth to provide a thorough understanding of the presentdisclosure. However, it is understood to those skilled in the art thatcertain embodiments of the present disclosure can be practiced withoutcertain, specific details. In other instances, well known methods,procedures, components, and circuitry have not been described in detailto avoid unnecessarily obscuring aspects of the embodiments.

Reference herein to “embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentcan be included in at least one example embodiment of the invention. Theappearances of this phrase in various places in the specification arenot necessarily all referring to the same embodiment, nor are separateor alternative embodiments mutually exclusive of other embodiments. Assuch, the embodiments described herein, explicitly and implicitlyunderstood by one skilled in the art, can be combined with otherembodiments.

Certain examples provide a network, such as a wireless network (e.g., awireless mesh network) used to connect multimedia playback devices, alsoreferred to herein as zone players. A controller, such as a controllerrunning on a smart phone (e.g., an Android™ smartphone, and AppleiPhone™, and Apple iPad™, and so on), a controller running on a personalcomputer, a dedicated controller (e.g., a Sonos CR 200™), and so on, canbe used to control music playback and/or other activity on the one ormore zone players connected to the network.

Certain embodiments provide a multi-room music system designed to playmusic throughout a house, vehicle, or other location via a wirelessnetwork. Unlike most other wireless networks, to simplify setup,encryption keys and SSIDs are automatically generated so a user does nothave to manually generate them. Reliable playback of music or othermultimedia content can be facilitated.

A traditional wireless access point system with a central hub relayingall the traffic typically does not provide a large enough range ofcoverage for an entire home or a desired level of performance forsynchronized digital music playback (e.g., no dead spots or low signalstrength). As long as each zone player is in range of another zoneplayer, the wireless network can determine how to route music or othercontent from the Internet and a user's computer to the rooms where theuser wants to enjoy it. Controllers are handed off transparently fromone zone player to the next so that a user can control the system fromthe location.

In certain embodiments, a controller can connect to the network forplayback via a variety of connections including via a local (e.g., home)wireless (e.g., WiFi) access point, such as a wireless router, and alocal node formed by a zone player on the network. Thus, the controllercan connect to the network and control multimedia playback or other zoneplayer function via either a wireless access point or a zone playerconnected to the network. In certain embodiments, a controller canexecute on a wireless device that can roam between a WiFi access pointand a local zone player node. In certain embodiments, each network isassociated with a different SSID, so the controller device is roamingbetween two different networks rather than roaming and connecting to thesame network when in range, for example.

In certain embodiments one or more zone players connected to thewireless network utilize radio technology in conjunction with a multipleantenna configuration designed to accommodate a user's hands holding thedevice to select music or other content. For example, a three antennaconfiguration allows a zone player to operate at maximum efficiency tosend and receive with an expected signal strength to provide a bestpossible wireless range and performance.

Certain embodiments provide an ability to connect a wireless device to ahidden network without the device or person knowing the network name orhaving to type in the network name (e.g., discovery and connection). Forexample, if a WiFi access point is not available, a controller (e.g., asmartphone controller) can connect to the hidden network withoutrequiring the user to type in the network name and without thesmartphone knowing the network exists.

In certain embodiments, setup technology searches for a wireless channelwith the least interference and sets up a wireless network that issecure by default. A mesh networking stack is provided to automaticallyoptimize the path on which data travels within a house or otherlocation, so playback is heard without interruption. In certainembodiments, multi-casting support is incorporated to facilitatedelivery of the same data (e.g., the same song) to multiple roomsefficiently.

In certain embodiments, with a wireless (e.g., WiFi) connection, thewireless mesh network (e.g., SonosNet™ network) is placed second on alist of available networks, such that if a smartphone controller is outof range of a WiFi access point, then the smartphone will use the meshnetwork as the access point. Thus, since data can pass through a zoneplayer as if the zone player was a WiFi access point, a local node zoneplayer can be used as a connection point for multimedia playback, Websurfing, and so on. In certain embodiments, a wireless device (e.g., asmartphone) can select between a WiFi access point and a local zoneplayer node as a network access point based on one or more criteria(e.g., which offers the best signal, least interference, and so on).

Embodiments of the systems, methods, apparatus, and/or articles ofmanufacture disclosed herein provide for network detection, control andmanagement in connection with multimedia playback devices. As describedin greater detail below, the systems, methods, apparatus, and/orarticles of manufacture disclosed herein provide users of a wirelessdevice, such as a phone or tablet computer, with an ability to connectto a hidden network. Systems, methods, apparatus, and/or articles ofmanufacture disclosed herein provide users of a wireless device, such asa phone or tablet computer, with an ability to monitor and switch amonga plurality of available connections to maintain access to control andplayback multimedia content.

Certain embodiments provide a method to connect a wireless device to ahidden network without the device or user network knowing or typing inthe network name. The example method includes detecting, via amultimedia playback device, a network connection request to an audionetwork, the audio network unspecified in the request and available buthidden at a location. The example method includes triggering, via themultimedia playback device, a connection phase to connect the wirelessdevice to the hidden audio network. The example method includesrevealing a network access point with a preset identifier to thewireless device to which the wireless device can connect using apredefined password valid during the connection phase. The examplemethod includes authenticating the wireless device with the audionetwork using the predefined password via the network access point andassociating the wireless device with the audio network with limitedconnectivity to the audio network during the connection phase. Theexample method includes disconnecting the wireless device from the audionetwork. The example method includes accepting a connection of thewireless to the audio network in an operational phase, the connectionenabled using information provided to the wireless device during theconnection phase and without the limited connectivity provided in theconnection phase.

Certain embodiments provide an example multimedia playback deviceconnected to a local multimedia playback network that is configured tonot provide an indicator of existence absent a command from themultimedia playback device, the multimedia playback device is toinitiate a connection phase for a device to connect to the hiddennetwork based on a user action at the multimedia playback device. Themultimedia playback device is to: reveal a network access point with apreset identifier to the wireless device to which the wireless devicecan connect using a predefined password valid during the connectionphase; authenticate the wireless device with the audio network using thepredefined password via the network access point and associating thewireless device with the audio network with limited connectivity to theaudio network during the connection phase; disconnect the wirelessdevice from the audio network; and accept a connection of the wirelessto the audio network in an operational phase, the connection enabledusing information provided to the wireless device during the connectionphase and without the limited connectivity provided in the connectionphase.

Certain embodiments provide a computer readable storage medium includinginstructions for execution by a processor. The instructions, whenexecuted, cause the processor to implement a method to connect a deviceto a playback network.

II. Example Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example systemconfiguration 100 in which one or more of the method and/or apparatusdisclosed herein can be practiced or implemented. By way ofillustration, the system configuration 100 represents a home withmultiple zones. Each zone, for example, represents a different room orspace, such as an office, bathroom, bedroom, kitchen, dining room,family room, home theater room, utility or laundry room, and patio.While not shown here, a single zone can cover more than one room orspace. One or more of zone players 102-124 are shown in each respectivezone. A zone player 102-124, also referred to as a playback device,multimedia unit, speaker, and so on, provides audio, video, and/oraudiovisual output. A controller 130 (e.g., shown in the kitchen forpurposes of illustration) provides control to the system configuration100. The system configuration 100 illustrates an example whole houseaudio system, though it is understood that the technology describedherein is not limited to its particular place of application or to anexpansive system like a whole house audio system 100 of FIG. 1.

FIGS. 2A, 2B, and 2C show example illustrations of zone players 200-204.The zone players 200-204 of FIGS. 2A, 2B, and 2C, respectively, cancorrespond to any of the zone players 102-124 of FIG. 1. While certainembodiments provide multiple zone players, an audio output can begenerated using only a single zone player. FIG. 2A illustrates a zoneplayer 200 including sound producing equipment 208 capable of generatingsound or an audio output corresponding to a signal received (e.g.,wirelessly and/or via a wired interface). The sound producing equipment208 of the zone player 200 of FIG. 2A includes a built-in amplifier (notshown in this illustration) and speakers (e.g., a tweeter, a mid-rangedriver, and/or a subwoofer. In certain embodiments, the zone player 200of FIG. 2A can be configured to play stereophonic audio or monauralaudio. In some embodiments, the zone player 200 of FIG. 2A can beconfigured as a component in a combination of zone players to playstereophonic audio, monaural audio, and/or surround audio. As describedin greater detail below, in some embodiments, the example zone player200 of FIG. 2A can also transmit a second signal to, for example, otherzone player(s) in the same or different zone(s), speaker(s),receiver(s), and so on. Transmission of the second signal can be partof, for example, a system in which multiple zone players, speakers,receivers, and so on, form a network to, for example, present mediacontent in a synchronization or distributed manner.

The example zone player 202 of FIG. 2B includes a built-in amplifier(not shown in this illustration) to power a set of detached speakers210. The speakers 210 of FIG. 2B can include, for example, any type ofloudspeaker. The zone player 202 of FIG. 2B can communicate a signalcorresponding to audio content to the detached speakers 210 via wiredand/or wireless channels. Instead of receiving and generating audiocontent as in FIG. 2A, the zone player 202 of FIG. 2B receives the audiocontent and transmits the same (e.g., after processing the receivedsignal) to the detached speakers 210. Similar to the example zone player200 of FIG. 2A, in some embodiments the zone player 202 can transmit asecond signal to, for example, other zone player(s) in the same ordifferent zone(s), speaker(s), receiver(s), and so on.

The example zone player 204 of FIG. 2C does not include an amplifier,but allows a receiver 214, or another audio and/or video type devicewith built-in amplification, to connect to a data network 128 of FIG. 1and to play audio received over the data network 128 via the receiver214 and a set of detached speakers 216. In addition to the wiredcouplings shown in FIG. 2C, the detached speakers 216 can receive audiocontent via a wireless communication channel between the detachedspeakers 216 and, for example, the zone player 204 and/or the receiver214. In some embodiments the zone player 202 can transmit a secondsignal to, for example, other zone player(s) in the same or differentzone(s), speaker(s), receiver(s), and so on.

Example zone players include a “Sonos® S5,” “Sonos Play:5,” “SonosPlay:3,” “ZonePlayer 120,” and “ZonePlayer 90,” which are offered bySonos, Inc. of Santa Barbara, Calif. Any other past, present, and/orfuture zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein. Azone player can also be referred to herein as a playback device, and azone player is not limited to the particular examples illustrated inFIGS. 2A, 2B, and 2C. For example, a zone player can include a wired orwireless headphone. In other examples, a zone player might include asubwoofer. In yet other examples, a zone player can include a sound bar.In an example, a zone player can include or interact with a dockingstation for an Apple iPod™ or similar device. In some embodiments, azone player can relay one or more signals received from, for example, afirst zone player to another playback device. In some embodiments, azone player can receive a first signal and generate an outputcorresponding to the first signal and, simultaneously or separately, canreceive a second signal and transmit or relay the second signal toanother zone player(s), speaker(s), receiver(s), and so on. Thus, anexample zone player described herein can act as a playback device and,at the same time, operate as a hub in a network of zone players. In suchinstances, media content corresponding to the first signal can bedifferent from the media content corresponding to the second signal.

FIG. 3 shows an example illustration of a wireless controller 300 in adocking station 302. The controller 300 can correspond to thecontrolling device 130 of FIG. 1. The controller 300 is provided with atouch screen 304 that allows a user to interact with the controller 300,for example, to retrieve and navigate a playlist of audio items, controloperations of one or more zone players, and provide overall control ofthe system configuration 100. In certain embodiments, any number ofcontrollers can be used to control the system configuration 100. Incertain embodiments, there can be a limit on the number of controllersthat can control the system configuration 100. The controllers might bewireless like wireless controller 300 or wired to the data network 128.Furthermore, an application running on any network-enabled portabledevices, such as an iPhone™, iPad™, Android™ powered phone, or any othersmart phone or network-enabled device can be used as a controller byconnecting to the data network 128. An application running on a laptopor desktop PC or Mac can also be used as a controller. Examplecontrollers include a “Sonos® Controller 200,” “Sonos® Controller foriPhone,” “Sonos® Controller for iPad,” “Sonos® Controller for Android,“Sonos® Controller for Mac or PC,” which are offered by Sonos, Inc. ofSanta Barbara, Calif. The flexibility of such an application and itsability to be ported to a new type of portable device is advantageous.

Referring back to the system configuration 100 of FIG. 1, a particularzone can contain one or more zone players. For example, the family roomof FIG. 1 contains two zone players 106 and 108, while the kitchen isshown with one zone player 102. Zones can be dynamically configured bypositioning a zone player in a room or space and assigning via thecontroller 130 the zone player to a new or existing zone. As such, zonescan be created, combined with another zone, removed, and given aspecific name (e.g., “Kitchen”), if so programmed. The zone players 102to 124 are coupled directly or indirectly to a data network, such as thedata network 128 shown in FIG. 1. The data network 128 is represented byan octagon in the figure to stand out from other components shown in thefigure. While the data network 128 is shown in a single location, it isunderstood that such a network can be distributed in and around thesystem configuration 100.

Particularly, the data network 128 can be a wired network, a wirelessnetwork, or a combination of both. In some embodiments, one or more ofthe zone players 102-124 are wirelessly coupled to the data network 128based on a proprietary mesh network. In some embodiments, one or more ofthe zone players 102-124 are wirelessly coupled to the data network 128using a non-mesh topology. In some embodiments, one or more of the zoneplayers 102-124 are coupled via a wire to the data network 128 usingEthernet or similar technology. In addition to the one or more zoneplayers 102-124 connecting to the data network 128, the data network 128can further allow access to a wide area network, such as the Internet.

In certain embodiments, the data network 128 can be created byconnecting any of the zone players 102-124, or some other connectingdevice, to a broadband router. Other zone players 102-124 can then beadded wired or wirelessly to the data network 128. For example, a zoneplayer (e.g., any of zone players 102-124) can be added to the systemconfiguration 100 by simply pressing a button on the zone player itself,which enables a connection to be made to the data network 128. Thebroadband router can be connected to an Internet Service Provider (ISP),for example. The broadband router can be used to form another datanetwork within the system configuration 100, which can be used in otherapplications (e.g., web surfing). The data network 128 can also be usedin other applications, if so programmed. Further, in certainembodiments, the data network 128 is the same network used for otherapplications in the household.

In certain embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows forsomeone to pass through zones while seamlessly listening to the audio.Further, zones can be put into a “party mode” such that all associatedzones will play audio in synchrony.

In certain embodiments, a zone contains two or more zone players. Forexample, the family room contains two zone players 106 and 108, and thehome theater room contains at least zone players 116, 118, and 120. Azone can be configured to contain as many zone players as desired, andfor example, the home theater room might contain additional zone playersto play audio from a 5.1 channel or greater audio source (e.g., a movieencoded with 5.1 or greater audio channels). If a zone contains two ormore zone players, such as the two zone players 106 and 108 in thefamily room, then the two zone players 106 and 108 can be configured toplay the same audio source in synchrony, or the two zone players 106 and108 can be paired to play two separate sounds in left and rightchannels, for example. In other words, the stereo effects of a sound canbe reproduced or enhanced through the two zone players 106 and 108, onefor the left sound and the other for the right sound. In certainembodiments, paired zone players can play audio in synchrony with otherzone players.

In certain embodiments, three or more zone players can be configured toplay various channels of audio that is encoded with three channels ormore sound. For example, the home theater room shows zone players 116,118, and 120. If the sound is encoded as 2.1 channel audio, then thezone player 116 can be configured to play left channel audio, the zoneplayer 118 can be configured to play right channel audio, and the zoneplayer 120 can be configured to play bass frequencies. Otherconfigurations are possible and depend on the number of zone players andthe type of audio. Further, a particular zone can be configured to playa 5.1 channel audio in one instance, such as when playing audio from amovie, and then dynamically switch to play stereo, such as when playingaudio from a two channel source.

In certain embodiments, two or more zone players can be sonicallyconsolidated to form a single, consolidated zone player. A consolidatedzone player (though made up of multiple, separate devices) can beconfigured to process and reproduce sound differently than anunconsolidated zone player or zone players that are paired, because aconsolidated zone player will have additional speaker drivers from whichsound can be passed. The consolidated zone player can further be pairedwith a single zone player or yet another consolidated zone player. Eachplayback device of a consolidated playback device is preferably set in aconsolidated mode.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

Sources of audio content to be played by zone players 102-124 arenumerous. Music from a personal library stored on a computer ornetworked-attached storage (NAS) can be accessed via the data network128 and played. Internet radio stations, shows, and podcasts can beaccessed via the data network 128. Music services that let a user streamand download music and audio content can be accessed via the datanetwork 128. Further, music can be obtained from traditional sources,such as a turntable or CD player, via a line-in connection to a zoneplayer, for example. Audio content can also be accessed through AirPlay™wireless technology by Apple, Inc., for example. Audio content receivedfrom one or more sources can be shared amongst the zone players 102 to124 via the data network 128 and/or the controller 130. Theabove-disclosed sources of audio content are referred to herein asnetwork-based audio information sources. However, network-based audioinformation sources are not limited thereto.

The example home theater zone players 116, 118, 120 are coupled to anaudio information source such as a television 132. In some examples, thetelevision 132 is used as a source of audio for the home theater zoneplayers 116, 118, 120, while in other examples audio information fromthe television 132 can be shared with any of the zone players 102-124 inthe audio system 100.

III. Example Playback Device

Referring now to FIG. 4, there is shown an example functional blockdiagram of a zone player 400 in accordance with an embodiment. The zoneplayer 400 of FIG. 4 includes a network interface 402, a processor 408,a memory 410, an audio processing component 412, a module 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players can not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 can beintegrated into another component. For example, the zone player 400could be constructed as part of a lamp for indoor or outdoor use.

Referring back to FIG. 4, the network interface 402 facilitates a dataflow between zone players and other devices on a data network (e.g., thedata network 128 of FIG. 1) and the zone player 400. In someembodiments, the network interface 402 can manage the assembling of anaudio source or file into smaller packets that are to be transmittedover the data network or reassembles received packets into the originalsource or file. In some embodiments, the network interface 402 canfurther handle the address part of each packet so that it gets to theright destination or intercepts packets destined for the zone player400. Accordingly, in certain embodiments, each of the packets includesan Internet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, the network interface 402 can include one or bothof a wireless interface 404 and a wired interface 406. The wirelessinterface 404, also referred to as an RF interface, provides networkinterface functions for the zone player 400 to wirelessly communicatewith other devices (e.g., other zone player(s), speaker(s), receiver(s),component(s) associated with the data network 128, and so on) inaccordance with a communication protocol (e.g., any of the wirelessstandards IEEE 802.11a, 802.11b, 802.11g, 802.11n, or 802.15). Toreceive wireless signals and to provide the wireless signals to thewireless interface 404 and to transmit wireless signals, the zone player400 of FIG. 4 includes one or more antennas 420. The wired interface 406provides network interface functions for the zone player 400 tocommunicate over a wire with other devices in accordance with acommunication protocol (e.g., IEEE 802.3). In some embodiments, a zoneplayer includes both of the interfaces 404 and 406. In some embodiments,a zone player 400 includes only the wireless interface 404 or the wiredinterface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software modules 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network. In someembodiments, a task might be for the zone player 400 to send audio datato another zone player or device on a network. In some embodiments, atask might be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmight be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software modules 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Incertain embodiments, the audio that is retrieved via the networkinterface 402 is processed and/or intentionally altered by the audioprocessing component 412. Further, the audio processing component 412can produce analog audio signals. The processed analog audio signals arethen provided to the audio amplifier 416 for play back through speakers418. In addition, the audio processing component 412 can includenecessary circuitry to process analog or digital signals as inputs toplay from zone player 400, send to another zone player on a network, orboth play and send to another zone player on the network. An exampleinput includes a line-in connection (e.g., an auto-detecting 3.5 mmaudio line-in connection).

The audio amplifier 416 is a device that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (for low frequencies), amid-range driver (middle frequencies), and a tweeter (high frequencies),for example. An enclosure can be sealed or ported, for example.

A zone player 400 can also be referred to herein as a playback device.An example playback device includes a Sonos® Play:5, which ismanufactured by Sonos, Inc. of Santa Barbara, Calif. The Play:5 is anexample zone player with a built-in amplifier and speakers. Inparticular, the Play:5 is a five-driver speaker system that includes twotweeters, two mid-range drivers, and one subwoofer. When playing audiocontent via the Play:5, the left audio data of a track is sent out ofthe left tweeter and left mid-range driver, the right audio data of atrack is sent out of the right tweeter and the right mid-range driver,and mono bass is sent out of the subwoofer. Further, both mid-rangedrivers and both tweeters have the same equalization (or substantiallythe same equalization). That is, they are both sent the samefrequencies, just from different channels of audio. Audio from Internetradio stations, online music and video services, downloaded music,analog audio inputs, television, DVD, and so on, can be played from aSonos® Play:5. While the Play:5 is an example of a zone player withspeakers, it is understood that a zone player with speakers is notlimited to one with a certain number of speakers (e.g., five speakers asin the Play:5), but rather can contain one or more speakers. Further, azone player can be part of another device, which might even serve apurpose different than audio (e.g., a lamp).

IV. Example Controller

Referring now to FIG. 5, there is shown an example controller 500, whichcan correspond to the controlling device 130 in FIG. 1. The controller500 can be used to facilitate the control of multi-media applications,automation and others in a system. In particular, the controller 500 isconfigured to facilitate a selection of a plurality of audio sourcesavailable on the network and enable control of one or more zone players(e.g., the zone players 102-124 in FIG. 1) through a wireless networkinterface 508. According to one embodiment, the wireless communicationsis based on an industry standard (e.g., infrared, radio, wirelessstandards IEEE 802.11a, 802.11b 802.11g, 802.11n, or 802.15). Further,when a particular audio is being accessed via the controller 500 orbeing played via a zone player, a picture (e.g., album art) or any otherdata, associated with the audio source can be transmitted from a zoneplayer or other electronic device to the controller 500 for display.

The controller 500 is provided with a screen 502 and an input interface514 that allows a user to interact with the controller 500, for example,to navigate a playlist of many multimedia items and to controloperations of one or more zone players. The screen 502 on the controller500 can be an LCD screen, for example. The screen 500 communicates withand is commanded by a screen driver 504 that is controlled by amicrocontroller (e.g., a processor) 506. The memory 510 can be loadedwith one or more application modules 512 that can be executed by themicrocontroller 506 with or without a user input via the user interface514 to achieve certain tasks. In some embodiments, an application module512 is configured to facilitate grouping a number of selected zoneplayers into a zone group and synchronizing the zone players for audioplay back. In some embodiments, an application module 512 is configuredto control the audio sounds (e.g., volume) of the zone players in a zonegroup. In operation, when the microcontroller 506 executes one or moreof the application modules 512, the screen driver 504 generates controlsignals to drive the screen 502 to display an application specific userinterface accordingly.

The controller 500 includes a network interface 508 that facilitateswireless communication with a zone player. In some embodiments, thecommands such as volume control and audio playback synchronization aresent via the network interface 508. In some embodiments, a saved zonegroup configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system. Further, a controller canbe integrated into a zone player.

It should be noted that other network-enabled devices such as aniPhone®, iPad® or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac®) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group including atleast two zone players from the controller 500. The zone players in thezone group can play audio in a synchronized fashion, such that all ofthe zone players in the zone group play back an identical audio sourceor a list of identical audio sources in a synchronized manner such thatno (or substantially no) audible delays or hiccups could be heard.Similarly, in some embodiments, when a user increases the audio volumeof the group from the controller 500, the signals or data of increasingthe audio volume for the group are sent to one of the zone players andcauses other zone players in the group to be increased together involume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplay back is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zoneplayers, for example, by starting with a single zone and then manuallylinking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would need to manually andindividually link each zone. The single command might include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed action. Other kinds of zone scenes can be programmed.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone can be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, and so on), a backup buzzer can be programmed to sound.The buzzer can include a sound file that is stored in a zone player, forexample.

V. Example Ad-Hoc Network

Certain particular examples will now be provided in connection withFIGS. 6-8B to describe, for purposes of illustration only, certain basesystems and methods to provide and facilitate connection to a playbacknetwork. FIG. 6 shows that there are three zone players 602, 604 and 606and a controller 608 that form a network branch that is also referred toas an Ad-Hoc network 610. The network 610 may be wireless, wired, or acombination of wired and wireless. In general, an Ad-Hoc (or“spontaneous”) network is a local area network or other small network inwhich there is no one access point for all traffic. With an establishedAd-Hoc network 610, the devices 602, 604, 606 and 608 can allcommunicate with each other in a “peer-to-peer” style of communication,for example. Furthermore, devices may come/and go from the network 610,and the network 610 will automatically reconfigure itself withoutneeding the user to reconfigure the network 610.

Using the Ad-Hoc network 610, the devices 602, 604, 606, and 608 canshare or exchange one or more audio sources and be grouped to play thesame or different audio sources. For example, the devices 602 and 604are grouped to playback one piece of music, and at the same time, thedevice 606 plays back another piece of music. In other words, thedevices 602, 604, 606 and 608, as shown in FIG. 6, form a HOUSEHOLD thatdistributes audio and/or reproduces sound. As used herein, the termHOUSEHOLD (provided in uppercase letters to disambiguate from the user'sdomicile) is used to represent a collection of networked devices thatare cooperating to provide an application or service. An instance of aHOUSEHOLD is identified with a household 10 (or household identifier).

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 610 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), SSID (a sequence ofalphanumeric characters as a name of a wireless network), and WEP keys(wired equivalent privacy or other security keys). In certainembodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., WEP keys). Inan embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 308) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 308 or a computingdevice, for example.

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously. In an environment that hasboth networks in use, it is assumed that at least one device in a systemis connected to both as a bridging device, thus providing bridgingservices between wired/wireless networks for others. The zone player 606in FIG. 6 is shown to be connected to both networks, for example. Theconnectivity to the network 612 is based on Ethernet while theconnectivity to other devices 602, 604 and 608 is based on Wireless. Itis understood, however, that in some embodiments each zone player 606,604, 602 may access the Internet when retrieving media from the cloud(e.g., Internet) via the bridging device. For example, zone player 602may contain a uniform resource locator (URL) that specifies an addressto a particular audio track in the cloud. Using the URL, the zone player602 may retrieve the audio track from the cloud, and ultimately play theaudio out of one or more zone players.

In certain embodiments, a rudimentary communication path is establishedto connect a zone player to a household or other location network. Inreference to FIG. 6, a zone player is not yet a member of a HOUSEHOLD.It is assumed that the zone player is to be added to become a member ofthe HOUSEHOLD by a cable or wireless. When the zone player is initiallyturned on, it executes an embedded module that is configured toestablish a rudimentary communication path with another device (e.g.,network-enabled). The rudimentary communication path facilitates theautomatic configuration of the zone player via another device. Thiscommunication path may operate over wireless and/or Ethernet protocols,as the zone player may be connected to one or both. In operation, thecommunication path does not negatively affect other devices in thevicinity and can reach all other members of the HOUSEHOLD (both CPs andZPs), if any are available. In certain embodiments, the communicationpath does not have to be direct between two devices and may be bridgedby one or more other devices. Because the communication path is onlyused for initial device configuration, it does not require significantperformance or sophisticated functionality. There are at least twoelements to establish the communication path: channel selection andpacket exchange.

In certain embodiments, selection of an appropriate transmission channel(e.g., a radio frequency (RF) channel) is primarily an exercise in twoconstraints: finding a channel that is quiet from a protocol (e.g.,802.11) viewpoint (e.g., minimal conflicting wireless traffic) andfinding a channel that is quiet from an RF viewpoint (e.g., minimalnoise from other signals). Both of these tests may be applied because ahome environment can have other RF (e.g., 2.4 GHz) traffic orpotentially other wireless access points.

Channel selection can be accomplished, for example, with a scanningtechnique, namely the device listens on each channel for a period oftime, looking for the presence of wireless beacons and other RF signals.In an embodiment, devices that are configured have a preferred channelfor the HOUSEHOLD, and devices that are not configured have apre-defined (default) channel or channels on which they rendezvous. Forexample, 802.11b/g channel 1 can be pre-configured as the defaultchannel. Alternatively, multiple channels, with a well-known frequencyhopping sequence, can be used by the devices (e.g., using an aperiodicfrequency change interval).

In certain embodiments, many hardware configurations only supportreception/transmission on a single channel at a given time. Also thereare configured and unconfigured devices that may use different channelsfor the bootstrap configuration and standard network operations(post-configuration communications). In certain embodiments, devices areplaced in a “configuration” mode, whereby they use the appropriatechannels for communication.

To enable communication between devices that are not part of the sameHOUSEHOLD, a packet exchange network infrastructure is developed.Probing messages are sent in such a way that they traverse both theEthernet and wireless networks, reaching any connected devices. Devicesthat are already in a HOUSEHOLD constitute a network infrastructure thatcan be used to exchange unicast and multicast/broadcast network framesbetween the devices. A device that is not yet in the HOUSEHOLD has amuch more limited networking capability and can only receive data fromdevices to which it is directly wired, and unencrypted messagesbroadcast to all wireless networks operating in a particular channel ofthe RF spectrum, for example.

In certain embodiments, an IP address of a new device is not known toany members of the HOUSEHOLD. If the device is purely wireless, it maynot have an IP address at all, or it may have an automatically assignedIP address that is inaccessible to other devices with IP addressesrespectively assigned by a DHCP server. To allow devices that are notmembers of the HOUSEHOLD to join the HOUSEHOLD, a transport may beconstructed that can get data one “hop” beyond the HOUSEHOLD networkinfrastructure.

In certain embodiments, packets of data are broadcasted among themembers of the HOUSEHOLD. The packets of data comprise a mixture of“probe” datagrams and IP broadcast. For example, the 802.11 “probe”datagrams are used to cross wireless network boundaries. In other words,the “probe” datagrams can be received by all listeners (e.g., otherdevices) on the channel, even those that are not configured with anSSID, because they are sent to the broadcasting satellite service (BSS)(e.g., FF:FF:FF:FF:FF:FF) to which all devices may be configured tolisten. An IP broadcast is used on the wired network segments and theHOUSEHOLD network infrastructure to enable a PC-based controller toparticipate while running with standard user privileges (which allowaccess only to IP-based network services), for example. Used together,the combination of “probe” datagrams and IP broadcast provides for abroadcast datagram transport that allows even devices that have not hadany networking parameters configured to communicate.

In certain embodiments, probe datagrams include a number of elements tofacilitate the configuration of other devices to join the HOUSEHOLD. Inan embodiment, each of the elements carries up to 255 bytes of data. Anelement contains data payload for each message used by the bootstrapprocedure to invite others to join the HOUSEHOLD. This element isrepeated as many times as necessary to carry the complete message. In anembodiment, the IP broadcast datagrams contain the same data payload asthe normal IP data payload.

Messages relating to the bootstrap procedure can be forwarded beyond theboundaries of an existing HOUSEHOLD network infrastructure (e.g.,including properly configured wireless devices and the wired network).Similarly, messages originating outside of the HOUSEHOLD networkinfrastructure can be forwarded into the infrastructure. Forwarding canbe accomplished in a mixed wireless/wired network environment withoutintroducing a broadcast storm. A broadcast storm is a state in which amessage that has been broadcast across a network results in moreresponses than necessary, and each response results in even moreresponses in a snowball effect, subsequently resulting in a networkmeltdown or lockup. In certain embodiments, the network is configured tohelp prevent such a broadcast storm or illegal broadcast messages. Toaccomplish this, two flags are included in the message body, forexample, “SENT_AS_PROBE” and “SENT_AS_IP_BROADCAST.” When a devicereceives a “probe” message, assumed using a “Sonos Netstart” SSID (orbroadcast BSS), the device forwards the message as an IP broadcastmessage (e.g., after setting a “SENT_AS_IP_BROADCAST: flag) if theSENT_AS_IP_BROADCAST flag is not already set. Similarly, when the devicereceives an IP broadcast with a user datagram protocol (UDP) payloadaddress to an appropriate port (e.g., port number 6969), the deviceforwards the message as a “probe” datagram (e.g., after setting a“SENT_AS_PROBE” flag) if the SENT_AS_PROBE flag is not already set. Thisallows messages related to the packet exchange both to enter and to exitthe HOUSEHOLD network infrastructure without causing a broadcast storm.

Using this method of broadcast communication, packets can be sentbetween a member of the HOUSEHOLD and a device to join the HOUSEHOLD onboth Ethernet and wireless networks. The device to join the HOUSEHOLDmay be a new device or a device previously configured with a differentnetwork (e.g., a device with a stale configuration in a differenthousehold), for example. In addition, if used sparingly, these broadcastmessages do not interfere with the normal operation of the network orattached devices. As a result, a communication path on an agreed channelhas been established between two devices.

In certain embodiments, to reduce or minimize impact on existingnetworks and to improve configuration security, a user can manuallyactivate the auto-configuration process. Manual user activation may beaccomplished by a specific action on each device that is being added tothe network. For example, if the user is installing a new HOUSEHOLD,containing one CP and two ZPs, the activation process can be manuallyactivated on each by, for example, powering off and on, pushing a resetbutton or pushing two or more specific buttons simultaneously on the ZPor CP. In an embodiment, the CP or ZP is powered up by the user, whichactivates the pre-installed module to start the bootstrap procedure.

For a ZP, if the device is unconfigured (e.g., factory defaultsettings), the device goes into a “sleep” mode where the device isawaiting an activation command. If the ZP has been previouslyconfigured, the ZP attempts to contact other members of its HOUSEHOLDnetwork. If the ZP is orphaned, namely the ZP was previously configured(e.g., perhaps, with another Ad-hoc network) and now is to be added tothe HOUSEHOLD (e.g., the ZP is obtained from a previous owner), the ZPcan attempt to contact its original network. It can be perceived thatthis operation will be unsuccessful but otherwise harmless, for example.Even in this configured state, the device can participate in therudimentary broadcast communication processes described above.

For a CP, if the device is unconfigured (e.g., factory defaultsettings), the CP presents the user with a description of how to startthe configuration process. If the CP device is configured, the CPattempts to contact other members of its HOUSEHOLD network. The CP mayalso be an orphaned device, in which case it performs similarly to thatof the ZP, for example.

In both cases, correctly configured devices establish networkcommunications and make themselves available for normal operation. Alldevices, including those previously configured, enter an “activationstate” when the user indicates that this is desired. At this point, theconfiguration process can begin.

In certain embodiments, device configuration is facilitated byexchanging data between two devices that are not necessarily directlyconnected. The exchange procedure is carried over a rudimentarycommunication path such as described previously. The sequence ofexchanging the data is initiated by the user or some other process, forexample, activating a reset button, to trigger the “activation” orconfiguration mode on the involved devices. Each device executes thissequence, and then exits the activation mode. FIG. 7 shows an embodimentthat involves a process of five exchanges of data.

Each of the data exchanges is referred to as a type of message: Alive,QueryNetParams, RespondNetParams, SetNetParams, and AckNetParams, eachof which is explained as follows.

An Alive message is a message indicating that a named ZP is availablefor configuration. The message includes at least a zpUUID (a zone player“universally” unique identifier) which is a globally unique identifierthat identifies the ZP sending the message.

A QueryNetParams message is a request from the CP to the ZP to respondwith the ZP's current network configuration information. The requestincludes at least a zpUUID, cpPK (e.g., an RSA public key of the CP) anda tid (a unique transaction identifier).

A RespondNetParams message is a response to the QueryNetParams message.The message includes the ZP's network configuration information (e.g.,HHID, WEP key and RSA public key). For security reasons, the WEP key isencrypted using the CP's public key that is only readable by the CP. Theresponse includes at least a zpUUID, netConfig (the ZP's current networkconfiguration parameters), zpPK (e.g., a public key for the ZP), and atid. In certain embodiments, a new ZP, set to factory defaults, can havewell-known parameter values, allowing the CP to determine that the ZP isunconfigured.

A SetNetParams message is a command message from the CP to the ZPindicating that the ZP should reconfigure its network parameters. TheWEP key is encrypted using the ZP's public key, and, therefore, onlyreadable by the ZP. The command includes at least a zpUUID, netConfigand tid. In certain embodiments, netConfig includes new configurationparameters for the ZP, as determined by the CP. The ZP saves this valuein its network configuration. In some cases, these parameters may matchthe ZP's existing configuration.

An AckNetParams message is a response to the SetNetParams messaging. Theresponse indicates that the SetNetParams message was received and thatthe network configuration contained therein has been successfullyapplied. The response includes at least a zpUUID and a tid.

In operation, after a user activates the configuration process (on bothZP and CP) at 751 in FIG. 7, the CP enters a state where it is willingto accept an Alive message. The CP remains in this state for a certain(e.g., specified or finite) period of time. The ZP enters an activationstate where it attempts rendezvous with a CP. The ZP remains in thisstate for a certain limited period of time. The ZP periodicallytransmits an Alive message until it either receives a QueryNetParamsmessage or exits the activation state.

At 752, the CP receives an Alive message. If the CP is in theconfiguration mode, it generates a new tid, and sends a QueryNetParamsmessage to the ZP. The CP may or may not have been configured at thispoint. In either case, the CP sends the QueryNetParams message. At 753,if the ZP is already in the activation state, the ZP responds to aQueryNetParams with its current network configuration. If the ZP isunconfigured (e.g., factory default settings), the ZP returns an emptyHHID and WEP key. If the ZP is previously configured, the ZP returns itscurrent configuration. The ZP also returns its public key such that theWEP key can be encrypted using the CP's public key, for example.

At 754, upon receiving the ZP's current configuration information, theCP decides on a course of action. In certain embodiments, most, but notall, of these options result in a SetNetParams message being sent to theZP. An example matrix of possible situations is as follows:

CP already configured CP not configured ZP already The CP sends aSetNetParams The CP sets its own configured message to the ZP containingconfiguration to match the ZP the CP's current net configuration, andthe configuration. ZP not The CP configuration process is sends aconfigured terminated. SetNetParams message to the ZP containing theCP's current net configuration. ZP not The CP sends a SetNetParams TheCP generates new configured message to the ZP containing configurationparameters. The the CP's current net parameters are sent to the ZPconfiguration. in a SetNetParams message. The CP sets its ownconfiguration to these values as well.

At 755, when the ZP receives a SetNetParams message, the ZP reconfiguresits own HHID and WEP key to match those contained in the network packet.Accordingly, the CP determines that it generates new configurationparameters in accordance with the following. For example, an HHID isprovided by the user via the CP user interface or automaticallygenerated by the CP. An SSID is automatically generated by the CP (e.g.,set to the same value as the HHID). A WEP Key is automatically generated(e.g., using a pseudo-random number generator, seeded with entropycollected by the CP). The CP probes the network looking for anacceptable channel (e.g., based on a variety of criteria, which mayinclude traffic and interference from other sources).

Following the activation process, devices that have been reconfiguredattempt to establish normal network communications using their newnetwork configuration parameters. In certain embodiments, if the CP orZP is not already in the activation state, receipt of messages isignored.

In certain embodiments, if there are multiple ZPs activatedsimultaneously (or substantially simultaneously), the devices canexecute this same sequence, independently of each other (e.g., the CP iscapable of multiple independent sessions). If multiple CPs areactivated, each can respond to a ZP's Alive message and execute thesequence. The first CP to deliver the SetNetParams to the ZP willconfigure it. In this case, the second CP may never get an AckNetParamsmessage because the ZP has exited the activate state. In certainembodiments, a transaction timeout may occur in the second CP, at whichpoint the CP may inform the user of the error or retry the entiresequence. If the CP retries the entire sequence, it will not reprogramthe ZP, for example.

Certain embodiments provide security in network communications. Forexample, to help ensure that wireless communication among the members ina HOUSEHOLD is secure, multiple issues in auto-configuration areresolved. For example, while packet exchange broadcasts may beunencrypted, public key cryptography is used to help ensure that WEPkeys are securely distributed. Because the network configuration processis automated and the data is transmitted over the network, in certainembodiments the auto-configuration process is started manually by auser. When one of the connected devices is removed from the HOUSEHOLD,the device is reset to a factory default configuration (e.g., erases WEPkeys and other private information) so that the device can no longeraccess to the network. In certain embodiments, a user can validate thathe or she has correctly configured one or more devices using avalidation/status user interface on the Control Point.

In certain embodiments, the configuration process uses public keycryptography to exchange WEP keys and other information that should notbe visible to any party sniffing the network. In an embodiment, anexchange is facilitated by designating a certificate authority (CA) toissue signed public key certificates. Each CP and ZP is factoryconfigured with a unique certificate, public and private key, in aformat that supports the RSA algorithm. The certificate is signed andissued by the designated CA, and includes a hash of the MAC address of adevice, for example. The CP and ZP exchange public keys, and WEP keysare encrypted using the public key. In certain circumstances, thedevices compare the MAC in received packets with that in the certificateto add an additional layer of security.

FIG. 8A shows a flowchart for an example method or process 800 forplayback device and network configuration. The process 800 can beimplemented in hardware, software or a combination of both as a method,a system or a process. In certain embodiments, the process 800 isimplemented for a handheld controller or a computing device. Tofacilitate the understanding of the process 800, the description hereinis based on a handheld controller, such as the controller 608 of FIG. 6,which shall not be considered as limiting with respect to the presentlydescribed technology.

In certain embodiments, a handheld controller is equipped with amechanism to allow a user to reset itself. In certain embodiments, thereset is done when the controller is powered up. At block 802, it isassumed that the controller is powered up. At block 804, it isdetermined whether the controller is configured. A configured controlleris ready for communication with other devices (e.g., zone players) thatmay or may not be on a network, such as a wireless network. In thecontext of FIG. 6, it means that the handheld device 608 is ready tocommunicate with each or all of the devices 602, 604, and 606 (assumingthat the devices 602, 604, and 606 have not been configured yet), forexample.

If the controller is configured, at block 806, where it determineswhether the device is a handheld (HH) controller device or a computer.For example, the device may be a dedicated handheld controller, apersonal computer or other type of device. In the illustratedembodiment, the type of device is determined because a handheldcontroller and a computer may provide a different display or graphicenvironment. If the device is a handheld controller, at block 808, thecontroller displays a screen for a user to proceed with the control ofone or more zone players connected to the playback network or replay ofcertain multimedia content via one or more zone players. If the deviceis a computer, the computer is loaded with a module that is executed todisplay an environment (e.g., a graphic user interface or GUI) thatallows a user to perform many tasks that may be done on the handheldcontroller in addition to other tasks that may be assisted by a pointingdevice (e.g., a mouse) or a keyboard.

At block 804, it is now assumed that the device is not configured, and,at block 812, it is determined if a user has activated the automaticconfiguration process. In an embodiment, the controller goes into a“sleep” mode after a predefined time should there be no activation ofthe configuration process. When the user activates the configurationprocess (e.g., via motion or button press), it is determined, at block814, whether the controller itself is coupled to an access point of anetwork or at least a member of the HOUSEHOLD (e.g., one zone player) iscoupled to the access point or an Ad-Hoc network. Typically, a GUI isprovided for a handheld or a computer. Accordingly, a display with arelevant message is displayed. After it is determined that either thecontroller itself or a zone player is coupled to a network, a user canpress “OK” in the displayed GUI, for example.

At block 818, the user can manually activate the automatic configurationprocess manually. In an embodiment, two buttons (e.g., labeledrespectively as “VOL” and “Mute”) can be pressed concurrently by theuser to initiate the automatic configuration process. At block 820, theprocess determines whether a valid response is received from a zoneplayer. If not, after a certain time 822, the process 800 goes back toblock 818 to reactivate the process or to block 814 via block 824 toprompt or remind the user regarding connection to the network.

In certain embodiments, a handheld controller is configured tofacilitate a new zone player to execute a household join process to jointhe HOUSEHOLD upon an appropriate channel. The channel can be agreedupon between the controller and the zone player. For example, when areset or multiple (e.g., two) buttons are pushed on the zone player to“activate” the household join process, the zone player scans through theavailable wireless channels, sending the “Alive” datagram for eachchannel in turn. The channels can be cycled through several times, forexample. When the zone player receives a QueryNetParams requestaddressed to the zone player, it stops the channel cycling. The zoneplayer remains locked on the channel on which it received the requestuntil a successful sequence ending in the configuration of the zoneplayer is completed (at which point it uses the specified channel), or atimeout expires (at which point it returns to its original channel orresumes cycling through channels and sending alive messages if theoverall timeout for the activation process has not expired).

In certain embodiments, although the zone player performs the channelcycling, the controller may also be configured to perform the channelcycling. However, when the controller is, for example, a personalcomputer, the zone player is typically configured to cycle through theavailable channels.

When a valid response is received from the zone player, the process 800determines whether the zone player provides its own network name (e.g.,HHID) at block 826. If the zone player does not have an HHID, whichindicates that the zone player is to be added into a wireless networknamed after an HHID provided by the device, then at block 828, the zoneplayer is instructed to join the wireless network. If the zone playerdoes have an HHID, which indicates that the device itself is to be addedinto the wireless network named after the HHID provided by the zoneplayer, the process exits at block 830.

After execution of the automatic configuration process is completed, amessage or an indication of completion is displayed. After the useracknowledges, at block 834, the user is asked to name the zone player,for example, “Dining” which indicated that the zone player is in thedining room. Subsequently, the process continues to block 406, describedabove.

FIG. 8B shows a flowchart for an example method or process 850 that canbe also implemented in hardware, software or a combination of both as amethod, a system or a process. In certain embodiments, the process 850is implemented for a zone player. To facilitate the understanding of theprocess 850, the illustrative description herein is based on a zoneplayer, such as the player 602 of FIG. 6, which shall not be consideredto limit the presently described technology.

When a zone player is powered up, the process 850, at block 852,determines whether the zone player is already registered or configured.For example, if the zone player is a used zone player, the zone playermay already be configured. If the zone player is configured, at block854, an indication of “registered” is shown. If the zone player is notconfigured, block 856 indicates an unconfigured ZP. At block 858,“normal” operation of the zone player is confirmed (e.g., through aninternal checkup).

At block 860, a user activates the automatic configuration process by,for example, pressing two buttons, labeled respectively as “VOL” and“Mute”, on the zone player at the same time. The automatic configurationprocess starts by sending out an Alive message, at block 862, asdescribed above. At block 864, the zone player awaits a response. If noresponse is received within or beyond a predefined time, the process 850goes to block 866 or block 858 to continue waiting for a response orrestart the process. When a response is received, the automaticconfiguration process continues at block 868, at which the zone playeris now part of the wireless network named after an HHID received eitherfrom a configured device or provided by itself.

VI. Example Hidden Network Access and Network Switching

As an alternative or addition to the connection systems and methodsdescribed above, certain additional embodiments for network connectionand switching are also described.

Certain embodiments provide a controller application running on awireless device to enable a user to connect to one of multiple availablenetworks. For example, using a controller application on Android™ smartphone, the user can connect to a playback device network via either oftheir household (or other location) wireless connection and the playbackdevice mesh network in order to control the playback devices on thenetwork. In certain embodiments, the wireless device controllerapplication can transition or roam between the two connections andmaintain control of content playback, such as audio music playback, onany of the connected playback device(s).

For example, FIG. 9 shows a multimedia playback system 900 in which awireless device 910 is attempting to connect to an available network toplayback multimedia content. The wireless device 910 can connect to oneor more available networks 920, 930 via one or more devices on thenetwork 920, 930. Each network 920, 930 can include one or more devicesor points of access for that network, for example. The wireless device910 (e.g., a controller, smartphone, tablet computer, etc.) can connectto a wireless access point 922, 932 and/or other device 924, 934 (e.g.,a zone player, speaker, other playback device, etc.) in the network.920, 930.

For example, if a user has no wireless access point in a home network orthe wireless controller device is not within range of a wireless accesspoint when the controller is first set up on a wireless device, awireless device on which the controller is being installed securelyestablishes a connection to the playback device network directly if thewireless device is within range one of the playback device devices orother components that form a part of the playback network. For example,using a join-household button on a zone player (an example playbackdevice), the user can configure his or her smartphone to operate as acontroller for the playback network.

Certain embodiments provide a service to run continuously in thebackground on the wireless controller to actively manage the decision ofwhether to connect to the playback network or another available wirelessnetwork in order to improve or maintain user experience as the usermoves from location to location.

For example, FIG. 10 depicts an example wireless device 1000 (e.g., thesame as or similar to the wireless device 910) including a signalstrength monitor 1010, a memory 1020 including a registry of networks1025, a processor 1030, a communication interface 1040, and a multimediacontent output 1050. The device 1000 can connect to an available networkusing the communication interface 1040 and facilitate playback and/orother communication of content via the output 1050 in conjunction withthe processor 1030. Using the signal strength monitor 1010, the device1000 can continuously (or periodically, etc.) monitor available networksidentified in the registry of networks 1020 and use the processor 1030to determine whether another available network is preferable forconnection than the currently connected network (e.g., stronger signal,better security, and so on).

FIG. 11 illustrates a flow diagram for an example method 1100 to connecta wireless device to a hidden network without the device or user networkthe network name or having to type in the network name.

At block 1105, a network connection request is initiated for a wirelessdevice to connect to an unspecified audio network available but hiddenat a location. For example, a connection request can be initiated via acontroller device (e.g., a smartphone, dedicated controller, tabletcomputer, laptop computer, etc.) within range of the audio network atthe location (e.g., a household, building, or other location). Asanother example, a connection request can be initiated via a buttonpress on a multimedia playback device connected to the audio network.

At block 1110, a network connection request to the audio network isdetected. The request can be detect via a multimedia playback device(e.g., a zone player, speaker, output, etc.) already connected to thehidden audio network, for example. The audio network is unspecified inthe request and is available but hidden at the location.

At block 1115, a connection phase is triggered to connect the wirelessdevice to the hidden audio network. The connection phase can betriggered via the multimedia playback device, for example. In certainexamples, the connection phase is triggered without sending a responseto the request from the multimedia playback device. In certainembodiments, no response is provided to broadcast probes unless anaction has recently been taken (e.g., one or more buttons recentlypressed) on the multimedia playback device and/or other networkcomponent.

At block 1120, a network access point is revealed with a presetidentifier to the wireless device to which the wireless device canconnect using a predefined password valid during the connection phase.In certain embodiments, the network access point is subsequently hiddenonce the identifier and password are provided to the connecting device.

At block 1125, the wireless device is authenticated with the audionetwork using the predefined password via the network access point. Thewireless device is associated with the audio network with limitedconnectivity to the audio network during the connection phase.

At block 1130, the wireless device is disconnected from the audionetwork. At block 1135, a connection of the wireless device to the audionetwork is accepted in an operational phase. The connection is enabledusing information provided to the wireless device during the connectionphase and without the limited connectivity provided in the connectionphase, for example.

At block 1140, network access is configured for the wireless deviceusing information provided to the wireless device during the connectionphase. At block 1145, playback of content is facilitated via themultimedia playback device on the audio network. For example, playbackcan be facilitated using the wireless device.

Thus, in certain embodiments, a multimedia playback device is connectedto a local multimedia playback network that is configured to hide (e.g.,not provide an indicator of its existence) absent a command from themultimedia playback device. The multimedia playback device initiates aconnection phase for a device to connect to the hidden network based ona user action at the multimedia playback device (e.g., a button press).The multimedia playback device then reveals a network access point witha preset identifier to the wireless device to which the wireless devicecan connect using a predefined password valid only during the connectionphase. The wireless device is authenticated with the audio network usingthe predefined password via the network access point and associated withthe audio network with limited connectivity to the audio network duringthe connection phase. The wireless device is then disconnected from theaudio network and can be reconnected to the audio network in anoperational phase. The connection in the operational phase is enabledusing information provided to the wireless device during the connectionphase and offers greater connectivity and access than the limitedconnectivity provided to the wireless device in the connection phase.

FIG. 12 illustrates a flow diagram for an example method 1200 tofacilitate switching between a wireless access point and a local node toaccess and control a networked multimedia system.

At block 1205, connection of a wireless device to a multimedia playbacknetwork is facilitated. For example, connection can be facilitated to avisible and/or hidden wireless network for communication, control,playback, and so on. Connection of the device to the network can befacilitated via an exchange of identifier and password information, forexample.

At block 1210, the wireless device is enabled to add the multimediaplayback network to a list of available networks for connection. Forexample, the wireless device can maintain a list of one or morenetworks/systems to which the device is authorized and/or otherwiseconfigured to connect.

At block 1215, one or more available networks within range of thewireless device are identified. For example, if the user has no WiFiaccess point or is not within range of a local access point when acontroller is first set up on a third-party device (e.g., an Android™smartphone, tablet, or other device), the device can securely establisha network connection directly if it is within range of a playback systemon one of the available networks.

At block 1220, a network characteristic, such as signal strength, ofidentified network(s) is monitored. For example, the wireless device caninclude a sensor to monitor and evaluate a received signal strength fromeach available wireless network.

At block 1225, an active wireless connection is actively switchedbetween identified networks based on the at least one monitored networkcharacteristics (e.g., signal strength, user-activity on the device,etc.) to optimize or improve user experience, playback quality, systemresponsiveness, and so on. In certain embodiments, if the connectiontransitions between networks, the wireless device transitions betweenthe two connections and maintains control of music playback on anyavailable networked device.

In certain embodiments, network roaming is facilitated using anapplication running on a wireless device that can roam between awireless (e.g., WiFi) access point and a local zone player or otherplayback device node. In certain embodiments, each network has its ownSSID, so the wireless device is roaming between two different networks,not just roaming and connecting to the same network when in range.

By using a controller application (e.g., a Sonos™ Controllerapplication) on a third-party wireless device (e.g., an Android device),a user can use either 1) his or her own WiFi connection or 2) the audioplayback network (e.g., SonosNet™ mesh network) to control the playbacksystem. In certain embodiments, the phone or other wireless device cantransition between the two connections and (relatively) seamlesslymaintain control of music playback on any of the connected, availabledevices.

In certain embodiments, with a wireless (e.g., WiFi) connection, thecontroller application software can intentionally place the playback(e.g., SonosNet™ mesh) network second or subsequent to one or more othernetwork connection options on a connectivity list, such that if a WiFiaccess point is listed first and the SonosNet™ network is second, andthe user's phone is out of range of the WiFi access point, then thephone will use the SonosNet as the access point to connect for playback.Thus, a local node one player can be put on a preferred list of networksand can be used as a connection point for web surfing, etc. (e.g., datawill pass through the zone player as if it is a WiFi access point).

In certain embodiments, if a user has no WiFi access point or is notwithin range of an access point when first setting up the controller ona third-party device (e.g., Android-based device), the phone or otherdevice can securely establish a playback network connection directly ifthe user is within range of a network-connected device (e.g., using ajoin-household button-press with respect to a bridge, zone player, orother playback device).

In certain embodiments, a service that runs continuously in thebackground on the third-party device to actively managing the decisionon whether to connect to the playback device (e.g., SonosNet™) oranother available wireless (e.g., WiFi) network in order to improve theexperience for the user as the user moves among multiple locations.

Thus, a third-party device can serve as a controller to set up andcontrol the playback system anywhere within range of the user's playbacksystem, making the user's wireless network, such as a home WiFi network,optional. Certain embodiments extend the WiFi range of a user's deviceto become a superset of the user's home WiFi coverage plus the playbackmesh network. Certain embodiments extend effective wireless rangeautomatically based on one or more criteria or parameters.

Certain embodiments provide a network for wireless playback ofmultimedia content at a location, such as a home. To support flexibilityin connecting to and controlling the playback network, security, such asWPA2 security, is provided with the one or more playback devices, suchas Sonos™ zone players, included in the network so that each playbackdevice in a mesh network can act as a wireless access point to athird-party device, such as a smartphone, being used as a controller.Once the controller on the third-party device has joined the playbacknetwork (e.g., using a customer's WiFi network), the controller is tosecurely obtain a WPA2 passphrase so that the controller canautomatically add the wireless playback network to the list of availablenetworks on the controller device. The controller will then be able touse the user wireless connection or the playback network wirelessnetwork. If the control device has no existing wireless connection butis within range of a playback device, bridge, dock, and so on, awireless device can securely join the local (e.g., household) networkusing the playback network directly without a separate wirelessconnection.

For example, in certain embodiments, the controller attempts to connectto a fictitious network with a specific SSID. This alerts the zoneplayer and the playback network that a controller is attempting to jointhe household. If the user has pressed the join household button orbuttons on a zone player and the zone player detects a device searchingfor the fictitious SSID, then the zone player makes itself visible sothat the zone player shows up in the controller device's wireless (e.g.,WiFi) scan. The controller now recognizes the visible playback networkand attempts to connect using a special fixed password, for example. Thezone player grants the connection but restricts communication to thetraffic to perform the network start protocol. The network start(netstart) protocol is the protocol that the controllers use to join ahousehold and to privately exchange network encryption keys. Thecontroller then disconnects, and the zone player returns to its normalhidden operation. The controller reconnects to the playback devicenetwork using the obtained network key.

In certain embodiments, a background service is used to determine whichwireless networks used on a controller device are on the same subnet asthe playback network. In certain embodiments, the service can monitorthe signal strength of the playback network and the networks identifiedabove. The service can actively switch the wireless connection of thecontroller device between the playback network and the other identifiednetworks based on signal strength and user activity on the device toimprove and optimize the user experience, for example. In certainembodiments, a controller application running on a device, such as asmartphone or tablet (e.g., an Android™ smartphone or tablet), uses adevice application programming interface (API) to modify (e.g., add,remove, edit, and so on) network (e.g., WiFi network) information.

Certain embodiments provide a packet transport the can be used tocommunicate short messages between wireless playback products. Certainembodiments provide a simplified packet transport which is used tocommunicate short messages between playback devices prior to the mainset up of a playback device network. For example, hardware and softwarecontrollers running on third-party hardware, such as a smartphone, canuse this simple packet transport to connect prior to the primary set upwith the playback device network. In certain embodiments, two basictransport transports are defined: an IP broadcast base transport and an802.11 probe request base transport, for example. In an example IPbroadcast-based transport, an IP packet with the source address equal tothe sender source address is provided along with a destination addressequal to the IP broadcast address. A real destination address (e.g., aSonos™ UUID) is embedded inside the message. In an example 802.11 proberequest-base transport, a source MAC (Media Access Control) address isequal to the sender's own wireless MAC address, a destination MAC ordestination BSSID is equal to a MAC broadcast address, and a realdestination address (e.g., Sonos™ UUID) is embedded inside informationelements within the probe. In an embodiment, the probe request is anidentifier such as “SonosNet™ start 1.0”. In certain embodiments, eachtransport packet has two bits indicating the transports on which thepacket has already been sent. For example, bits can indicate packet hasalready been sent as an IP broadcast or sent as an 802.11 probe. Whenthe zone player initiates the transmission of the packet, the zoneplayer sends the packet twice, once using each transport (e.g., with anappropriate set syndicate the transport being used). When the controllerinitiates the transmission of the packet, the controller sends thepacket one using IP broadcast (e.g., with appropriate bit set). Incertain embodiments, however, the controller sends the packet twice.When the net start application on the zone player receives a net startpacket, it retransmits the packet on any transports that have notpreviously been used, setting the appropriate bits to indicate thetransport. Thus, each zone player receiving a net start packet as aprobe request forwards it once as an IP broadcast on the playback meshnetwork, and each zone player receiving a packet as an IP broadcastsubmits it once as a probe request.

In certain embodiments, a plurality of netstart protocol messages can beused to facilitate the netstart protocol for a new device, such as acontroller (CR), connecting to the network. For example, messages caninclude:

Message Name Direction Purpose R_NS_ALIVE_UNICAST_REQUEST CR to “world”(optional) A broken CR that is unable to receive IP broadcasts tells allZPs to send their R_NS_ALIVE messages as unicasts to its IP addressR_NS_ALIVE ZP to “world” Announces a ZP's presence (or unicast- when theuser pushes see above) mute + volume up R_NS_QUERY CR to ZP A CR tellsthe ZP its RSA public key, and asks the ZP for its own RSA public key,home channel, HouseholdID (≈SSID), and AES key R_NS_RESPONSE ZP to CR AZP responds with its own RSA public key, home channel, HouseholdID, andAES key (the latter three will be “blank” in a “factory reset” state,and will be encrypted using the CR's RSA public key) R_NS_ASSESS_CHANSCR to ZP A CR asks a ZP to examine each of its possible channels andreport the best one R_NS_RESPOND_CHANS ZP to CR A ZP responds with itsassessment of which channel is best R_NS_SET CR to ZP A CR tells a ZPwhat channel, HouseholdID, and AES key to use (encrypted with ZP's RSApublic key) R_NS_ACK ZP to CR A ZP responds, acknowledging that itobeyed the instructions specified in the R_NS_SET R_NS_REVERTCHAN CR toZP A CR tells a ZP that the NetStart protocol is complete and the ZPshould revert to its “home” channel R_NS_GETCHAN CR to ZP A CR asks a ZPwhat channel the household is using (used by the UI for setting thechannel; NOT used at all during setup) R_NS_RESP_GETCHAN ZP to CR A ZPresponds to the CR telling it the channel number (used by the UI forsetting the channel; NOT used at all during setup) R_NS_SETCHAN CR toZPA CR tells all ZPs in a household what channel to use (used by the UIfor setting the channel; NOT used at all during setup)

In certain embodiments, an example sequence between a factory reset CRand a factory reset ZP can be illustrated according to the messagesabove as:

-   -   1. R_NS_ALIVE_UNICAST_REQUEST (from CR to any listening ZP)    -   2. R_NS_ALIVE (from ZP so that CR and ZP find one another)    -   3. R_NS_QUERY (from CR to ZP)    -   4. R_NS_RESPONSE (CR asks ZP for its RSA public key+network        parameters−which come back blank because the ZP is factory        reset)    -   5. R_NS_ASSESS_CHANS (CR asks ZP to perform a channel assessment    -   6. R_NS_RESPOND_CHANS (and ZP responds with an assessment of a        best channel for communication)    -   7. R_NS_SET (CR generates a new HouseholdID and AES key, and        programs it into the ZP, along with the channel determined        during R_NS_ASSESS_CHANS)    -   8. R_NS_ACK (ZP responds in acknowledgement)

In certain embodiments, an example sequence between a factory reset CRand a non-factory reset ZP can be illustrated according to the messagesabove as:

-   -   1. R_NS_ALIVE_UNICAST_REQUEST    -   2. R_NS_ALIVE (CR and ZP find one another)    -   3. R_NS_QUERY    -   4. R_NS_RESPONSE (CR asks ZP for its RSA public key+network        parameters−which come back populated)    -   5. R_NS_REVERTCHAN (CR locally applies network parameters and        instructs the ZP to return to its home channel immediately)

In certain embodiments, an example sequence when using a CR to add a ZPto an existing household can be illustrated according to the messagesabove as:

-   -   1. R_NS_ALIVE_UNICAST_REQUEST    -   2. R_NS_ALIVE (CR and new ZP find one another)    -   3. R_NS_QUERY    -   4. R_NS_RESPONSE (CR asks its associated ZP for the network        parameters)    -   5. R_NS_QUERY    -   6. R_NS_RESPONSE (CR gets the RSA public key of the new ZP,        ignoring all other network parameters)    -   7. R_NS_SET    -   8. R_NS_ACK (CR programs the channel, HouseholdID, and AES key        into the new ZP)

In certain embodiments, the user presses one or more buttons on a zoneplayer to connect to a wireless playback network. The zone player cyclesbetween each of a number of possible channels (e.g., three possiblechannels). The zone player sends alive messages on each of the possiblechannels and then waits a short time for a response. The controller sitson one channel listing for the alive messages. When the controller hearsan alive message, the controller sends the originating zone player aquery. Upon receipt of the query, the zone player halts its cyclingbetween channels. The remaining netstart handshake takes place on thechannel on which the zone player landed when contacted by thecontroller. At the end of the sequence, when the zone player receives anetwork set message, the zone player switches to a specified channel.Alternatively, when the zone player receives a revert channel message,the zone player returns to its “home” channel.

In certain embodiments, when the user presses one or buttons on the zoneplayer, the zone player cycles between each of a number of possiblechannels (e.g., three possible channels) sending alive messages and thenwaiting a short time for a response. The controller sends and receivesIP broadcasts. A new wireless zone player communicates with thecontroller by relying on the net start behavior of forwarding receivenet start 802.11 probe requests onto the playback network as IPbroadcasts and of forwarding received IP broadcast from the playbacknetwork as 802.11 probe requests. When zone player receives a netstartset message, the zone player switches to the specified channel.Alternatively, when zone player receives a revert channel message, thezone player returns to its home channel.

In certain embodiments, the controller uses a wireless chip, such as anAR6002 wireless chip, which has a hardcoded firmware implementation ofan 802.11g client. This firmware can, for example, probe for accesspoints on a specified list of channels and report back content ofinformation elements from their beacons and probe responses. Thefirmware can also, for example, associate with the specified accesspoint, such as an SSID, a BSSID, an advanced encryption standard (AES)key, and so on. Netstart can be built on top of this firmware capabilitysuch that when the user presses buttons on the zone player to connect tothe network, the zone player still cycles between each of the availablechannels sending and allied message and then waiting a short time forresponse. While the zone player is cycling between the availablechannels, the zone player also includes a special information element inits probe responses indicating that the zone player is in net startmode. The controller continuously scans for access points, cyclingbetween the possible channels at a rate faster than the zone player andsending probes which include a special information element indicatingthat the controller is searching for zone player. If a zone player innet start mode receives a broadcast probe from a controller searchingfor a zone player, as identified by the special information element, thezone player aborts channel scanning and respond to the broadcast probe.The controller looks at the scan results for an access point with thespecial information element. If it finds such an access point, the zoneplayer associates with the access point without security. The special“no security” association currently allows a controller and the playbacknetwork to exchange MAC broadcast frames. In certain embodiments, thesecurity is tightened to allow the controller and the zone player toexchange net start broadcasts only. That is, only MAC broadcasts thatare also IP broadcasts including, for example, a UDP datagram withdestination port 6969 can be exchanged. The stricter filter makes the“no security” association more limited and, hence, less of a securityrisk. In certain embodiments, if the zone player is factory reset anddoes not have a household ID, the zone player uses an SSID of a genericform for the temporary association. In certain embodiments, there is aspecial “safe association” mode for manufacturing test used with zoneplayer that includes an extra MAC address of the one and only controllercommitted to associate in its beacons and probe responses.

Once an association relationship is established between the controllerand the zone player, the net start handshake occurs via IP broadcast.Once the controller identifies the network AES key, the controller dropsis insecure Association with the zone player and re-creates theassociation securely using the AES key with full permission access theplayback network.

In certain embodiments, a more constrained version of controllerimplementation is provided. For example, the controller cannot set ordetect arbitrary information elements in probe requests or proberesponses. Some controller devices, such as smartphones, cannot see anaccess point that is not sending beacons these phones are able toassociate to zone players that are not sending beacons, for example. Inorder to do this, the zone players made to look like a standard outaccess point during household discovery by the controller device. Whenthe user hits the buttons on the zone player connected to a network, thezone player tells the wireless driver to drop all probes and associationrequests from third-party devices in addition to doing channel scanningand waiting for the life message. The controller, such as a smart phone,attends to connect to a network with SSID set to net start which causesthe device to send targeted probes for that SSID in addition tobroadcast all probes. When the wireless driver on the zone player seesthe targeted probes for net start, the zone player signals a net startvia a net link. In certain embodiments, the zone player does not respondto the probe. Net start then switches to the quote home quote channel tohelp ensure that there is a path for DHCP traffic and enables a wirelessdriver to respond to broadcast and targeted probes to the normal SSID.Additionally, net start starts sending beacons with the SSID in them.The wireless device sees an IP with that SSID starting with a householdID number and assumes that the device is a zone player. The wirelessdevice then attempts WPA2 authentication with a password that is onlyvalid during net start mode on the zone player. The zone player allowsthe controller device to associate with the network and provides limitednetwork, tip conductivity privacy (e.g., enough for DHCP and net start).The controller device does it conducts the IP-based net start protocoldescribed above to join the household. The wireless controller deviceuses information obtained from the zone player to set up a correctnetwork configuration (e.g., SSID and permanent WPA2 passphrase).

Various inventions have been described in sufficient detail with acertain degree of particularity. It is understood to those skilled inthe art that the present disclosure of embodiments has been made by wayof examples only and that numerous changes in the arrangement andcombination of parts can be resorted without departing from the spiritand scope of the present disclosure as claimed. While the embodimentsdiscussed herein can appear to include some limitations as to thepresentation of the information units, in terms of the format andarrangement, the embodiments have applicability well beyond suchembodiment, which can be appreciated by those skilled in the art.Accordingly, the scope of the present disclosure is defined by theappended claims rather than the forgoing description of embodiments.

We claim:
 1. A method to connect a wireless device to a hidden network without the device or user knowing or typing in the network name, the method comprising: detecting, via a multimedia playback device, a network connection request by the wireless device, wherein the network connection request does not specify an audio network and wherein the audio network is available for connection but hidden such that the wireless device is not aware of the hidden audio network; triggering, via the multimedia playback device, a network connection phase to automatically connect the wireless device to the hidden audio network; revealing a network access point with a preset identifier such that the network access point is detectable by the wireless device, wherein revealing the network access point triggers the wireless device to connect to the network access point using a predefined password valid during the network connection phase; authenticating the wireless device with the audio network using the predefined password via the network access point and associating the wireless device with the audio network with limited connectivity to the audio network during the network connection phase; after authenticating the wireless device with the audio network, disconnecting the wireless device from the audio network; and after disconnecting the wireless device from the audio network, accepting a connection of the wireless device to the audio network in an operational phase, the connection enabled using information provided to the wireless device during the network connection phase and without being restricted to the limited connectivity provided in the network connection phase.
 2. The method of claim 1, further comprising initiating the network connection request for the wireless device to connect to the unspecified hidden audio network via a wireless controller device.
 3. The method of claim 2, wherein initiating occurs via button press on the multimedia playback device connected to the audio network.
 4. The method of claim 1, wherein triggering the connection phase occurs without sending a response to the request from the multimedia playback device.
 5. The method of claim 1, further comprising subsequently hiding the network access point after connection by the wireless device.
 6. The method of claim 1, wherein no response is provided to broadcast probes unless one or more buttons have recently been pressed on the multimedia playback device.
 7. The method of claim 1, further comprising configuring, using information provided to the wireless device, connection and playback on the audio network.
 8. The method of claim 1, further comprising facilitating, using the wireless device, playback via the multimedia playback device on the audio network.
 9. A multimedia playback device connected to a local multimedia playback network that is configured to not provide an indicator of existence absent a command from the multimedia playback device, the multimedia playback device to initiate a network connection phase for a wireless device to connect to the hidden network, the multimedia playback device to: detect a network connection request by the wireless device, wherein the network connection request does not specify an audio network and wherein the audio network is available for connection but hidden such that the wireless device is not aware of the hidden audio network; trigger the network connection phase to automatically connect the wireless device to the hidden audio network; reveal a network access point with a preset identifier such that the network access point is detectable by the wireless device, wherein revealing the network access point triggers the wireless device to connect to the network access point using a predefined password valid during the network connection phase; authenticate the wireless device with the audio network using the predefined password via the network access point and associating the wireless device with the audio network with limited connectivity to the audio network during the network connection phase; after authenticating the wireless device with the audio network, disconnect the wireless device from the audio network; and after disconnecting the wireless device from the audio network, accept a connection of the wireless device to the audio network in an operational phase, the connection enabled using information provided to the wireless device during the network connection phase and without being restricted to the limited connectivity provided in the network connection phase.
 10. The system of claim 9, wherein the wireless device comprises a wireless controller device and wherein the wireless controller device initiates the network connection request for the wireless device to connect to the unspecified hidden audio network.
 11. The system of claim 10, wherein the initiating occurs via button press on the multimedia playback device connected to the audio network.
 12. The system of claim 9, wherein the connection phase is triggered without sending a response to the request from the multimedia playback device.
 13. The system of claim 9, wherein the network access point is subsequently hidden after connection by the wireless device.
 14. The system of claim 9, wherein no response is provided to broadcast probes unless one or more buttons have recently been pressed on the multimedia playback device.
 15. A non-transitory computer readable storage medium including instructions for execution by a processor, the instructions, when executed, cause the processor to implement a method to connect a device to a playback network, the method comprising: detecting, via a multimedia playback device, a network connection request by the wireless device, wherein the network connection request does not specify an audio network and wherein the audio network is available for connection but hidden such that the wireless device is not aware of the hidden audio network; triggering, via the multimedia playback device, a network connection phase to automatically connect the wireless device to the hidden audio network; revealing a network access point with a preset identifier such that the network access point is detectable by the wireless device, wherein revealing the network access point triggers the wireless device to connect to the network access point using a predefined password valid during the network connection phase; authenticating the wireless device with the audio network using the predefined password via the network access point and associating the wireless device with the audio network with limited connectivity to the audio network during the network connection phase; after authenticating the wireless device with the audio network, disconnecting the wireless device from the audio network; and after disconnecting the wireless device from the audio network, accepting a connection of the wireless device to the audio network in an operational phase, the connection enabled using information provided to the wireless device during the network connection phase and without being restricted to the limited connectivity provided in the network connection phase.
 16. The medium of claim 15, further comprising initiating the network connection request for the wireless device to connect to the unspecified hidden audio network via a wireless controller device.
 17. The medium of claim 16, wherein initiating occurs via button press on the multimedia playback device connected to the audio network.
 18. The medium of claim 15, wherein triggering the connection phase occurs without sending a response to the request from the multimedia playback device.
 19. The medium of claim 15, further comprising subsequently hiding the network access point after connection by the wireless device.
 20. The medium of claim 15, wherein no response is provided to broadcast probes unless one or more buttons have recently been pressed on the multimedia playback device. 